Computerized systems and methods for managing and monitoring services and modules on an online platform

ABSTRACT

The present disclosure may be directed to systems and methods for managing and monitoring services and modules. The system may include receiving, from a user device, a request to perform a test on a target application programming interface; calling the target application programming interface; and retrieving a search result page associated with the target application programming interface. The system may include retrieving a rule based on the target application programming interface and applying the rule to the retrieved search result page associated with the target application programming interface. The system may include determining whether to implement the target application programming interface based on the results of the applied rule.

TECHNICAL FIELD

The present disclosure generally relates to computerized systems andmethods for managing and monitoring services and modules. In particular,embodiments of the present disclosure relate to inventive andunconventional systems related to implementing services and modules bycalling target application programming interfaces and applying rules tothe services and modules.

BACKGROUND

Service and module implementation by developers often relies on testingservices and modules in order to successfully deploy and manage new andexisting services and modules. When services and modules are not tested,the intended behavior of the service or module may not be preserved.Service and module tests include controls that are critical topreserving the intended behavior of the service or module, especiallywhen the service or module is modified or when new services and modulesare implemented.

Properly testing services and modules is critically important tomaintaining the quality of any online platform. However, managing andmonitoring services and modules may be difficult when online platformshave a large number of services and modules, which are difficult totrack. This difficulty in managing and monitoring a large number ofservices and modules is problematic when the intended behavior of theservices or modules are not preserved. Furthermore, manually testingeach service or module is often difficult and time-consuming for anorganization.

The quality of an organization's online platform and, consequently, theexperiences of users are severely reduced when the online platformincludes faulty services and modules that have not been tested properly.The quality of an organization's online platform would be significantlyimproved if the online platform automatically and efficiently managedand monitored services and modules implemented tested services andmodules accordingly.

Therefore, there is a need for improved systems and methods for managingand monitoring services and modules.

SUMMARY

One aspect of the present disclosure is directed to a system formanaging and monitoring services and modules. The system may include amemory storing instructions and at least one processor configured toexecute the instructions to receive, from a user device, a request toperform a test on a target application programming interface; call thetarget application programming interface; and retrieve a search resultpage associated with the target application programming interface. Theinstructions may include retrieving a rule based on the targetapplication programming interface; applying the rule to the retrievedsearch result page associated with the target application programminginterface; and based on the results of the applied rule, determiningwhether to implement the target application programming interface.

Another aspect of the present disclosure is directed to a method formanaging and monitoring services and modules. The method may includereceiving, from a user device, a request to perform a test on a targetapplication programming interface; calling the target applicationprogramming interface; and retrieving a search result page associatedwith the target application programming interface. The method mayinclude retrieving a rule based on the target application programminginterface; applying the rule to the retrieved search result pageassociated with the target application programming interface; and basedon the results of the applied rule, determining whether to implement thetarget application programming interface.

Yet another aspect of the present disclosure is directed to a system formanaging and monitoring services and modules. The system may include amemory storing instructions and at least one processor configured toexecute the instructions to receive, from a user device, a request toperform a test on a target application programming interface; call thetarget application programming interface; and retrieve a search resultpage associated with the target application programming interface. Theinstructions may include retrieving a rule based on the targetapplication programming interface; loading a uniform resource linkassociated with the target application programming interface; andextracting data from the retrieved search result page, wherein the ruleis applied to the extracted data, and the user device specifies theextracted data in accordance with the rule. The instructions may includeapplying the rule to the extracted data from the retrieved search resultpage associated with the target application programming interface; andbased on the results of the applied rule, determining whether toimplement the target application programming interface.

Other systems, methods, and computer-readable media are also discussedherein.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A is a schematic block diagram illustrating an exemplaryembodiment of a network comprising computerized systems forcommunications enabling shipping, transportation, and logisticsoperations, consistent with the disclosed embodiments.

FIG. 1B depicts a sample Search Result Page (SRP) that includes one ormore search results satisfying a search request along with interactiveuser interface elements, consistent with the disclosed embodiments.

FIG. 1C depicts a sample Single Detail Page (SDP) that includes aproduct and information about the product along with interactive userinterface elements, consistent with the disclosed embodiments.

FIG. 1D depicts a sample Cart page that includes items in a virtualshopping cart along with interactive user interface elements, consistentwith the disclosed embodiments.

FIG. 1E depicts a sample Order page that includes items from the virtualshopping cart along with information regarding purchase and shipping,along with interactive user interface elements, consistent with thedisclosed embodiments.

FIG. 2 is a diagrammatic illustration of an exemplary fulfillment centerconfigured to utilize disclosed computerized systems, consistent withthe disclosed embodiments.

FIG. 3 is a schematic block diagram illustrating an exemplary embodimentof a network comprising computerized systems for managing and monitoringservices and modules, consistent with disclosed embodiments.

FIG. 4 depicts a process for managing and monitoring services andmodules, consistent with disclosed embodiments.

DETAILED DESCRIPTION

The following detailed description refers to the accompanying drawings.Wherever possible, the same reference numbers are used in the drawingsand the following description to refer to the same or similar parts.While several illustrative embodiments are described herein,modifications, adaptations and other implementations are possible. Forexample, substitutions, additions, or modifications may be made to thecomponents and steps illustrated in the drawings, and the illustrativemethods described herein may be modified by substituting, reordering,removing, or adding steps to the disclosed methods. Accordingly, thefollowing detailed description is not limited to the disclosedembodiments and examples. Instead, the proper scope of the invention isdefined by the appended claims.

Embodiments of the present disclosure are directed to systems andmethods configured for managing and monitoring services and modules. Thedisclosed embodiments may include a monitoring platform that sends arequest to perform a test on a target service or module to a pageresponse system. The page response system may call a target applicationprogramming interface or a target webpage uniform resource link (URL)based on the request. Based on the call by the page response system, awebpage with an implemented module or a webpage may be retrieved andsent to the page response system. The page response system may parse theretrieved webpage by loading the URL for the retrieved webpageassociated and extracting data from the retrieved webpage.

The page response system may send the retrieved webpage to a ruleapplication system, which may retrieve at least one rule from based onthe characteristics of the webpage. The rule application system mayapply the retrieved rule to the data extracted from the webpage. Theretrieved rule may include a predetermined condition for determiningwhether the webpage is normal or abnormal. The rule application systemmay send the results of the applied rule to the monitoring platform.Based on the characteristics of the webpage and the results of appliedrule, the monitoring platform may instruct the rule application systemto send an alert or analytics of the results of the applied rule to atleast one user device.

In some embodiments, if the results indicate that the webpage isabnormal, then the monitoring platform may not implement applicationprogramming interface or the webpage. If the results indicate that thewebpage is normal, then the monitoring platform may implement theapplication programming interface or the webpage. The monitoringplatform may send a response to a device or a user where the responsemay include an indication of whether the application programminginterface or the webpage has been implemented, analytical dataassociated with the applied rule, an indication of whether alerts oranalytics were sent to user devices, etc.

Referring to FIG. 1A, a schematic block diagram 100 illustrating anexemplary embodiment of a system comprising computerized systems forcommunications enabling shipping, transportation, and logisticsoperations is shown. As illustrated in FIG. 1A, system 100 may include avariety of systems, each of which may be connected to one another viaone or more networks. The systems may also be connected to one anothervia a direct connection, for example, using a cable. The depictedsystems include a shipment authority technology (SAT) system 101, anexternal front end system 103, an internal front end system 105, atransportation system 107, mobile devices 107A, 107B, and 107C, sellerportal 109, shipment and order tracking (SOT) system 111, fulfillmentoptimization (FO) system 113, fulfillment messaging gateway (FMG) 115,supply chain management (SCM) system 117, warehouse management system119, mobile devices 119A, 119B, and 119C (depicted as being inside offulfillment center (FC) 200), 3^(rd) party fulfillment systems 121A,121B, and 121C, fulfillment center authorization system (FC Auth) 123,and labor management system (LMS) 125.

SAT system 101, in some embodiments, may be implemented as a computersystem that monitors order status and delivery status. For example, SATsystem 101 may determine whether an order is past its Promised DeliveryDate (PDD) and may take appropriate action, including initiating a neworder, reshipping the items in the non-delivered order, canceling thenon-delivered order, initiating contact with the ordering customer, orthe like. SAT system 101 may also monitor other data, including output(such as a number of packages shipped during a particular time period)and input (such as the number of empty cardboard boxes received for usein shipping). SAT system 101 may also act as a gateway between differentdevices in system 100, enabling communication (e.g., usingstore-and-forward or other techniques) between devices such as externalfront end system 103 and FO system 113.

External front end system 103, in some embodiments, may be implementedas a computer system that enables external users to interact with one ormore systems in system 100. For example, in embodiments where system 100enables the presentation of systems to enable users to place an orderfor an item, external front end system 103 may be implemented as a webserver that receives search requests, presents item pages, and solicitspayment information. For example, external front end system 103 may beimplemented as a computer or computers running software such as theApache HTTP Server, Microsoft Internet Information Services (IIS),NGINX, or the like. In other embodiments, external front end system 103may run custom web server software designed to receive and processrequests from external devices (e.g., mobile device 102A or computer102B), acquire information from databases and other data stores based onthose requests, and provide responses to the received requests based onacquired information.

In some embodiments, external front end system 103 may include one ormore of a web caching system, a database, a search system, or a paymentsystem. In one aspect, external front end system 103 may comprise one ormore of these systems, while in another aspect, external front endsystem 103 may comprise interfaces (e.g., server-to-server,database-to-database, or other network connections) connected to one ormore of these systems.

An illustrative set of steps, illustrated by FIGS. 1B, 1C, 1D, and 1E,will help to describe some operations of external front end system 103.External front end system 103 may receive information from systems ordevices in system 100 for presentation and/or display. For example,external front end system 103 may host or provide one or more web pages,including a Search Result Page (SRP) (e.g., FIG. 1B), a Single DetailPage (SDP) (e.g., FIG. 1C), a Cart page (e.g., FIG. 1D), or an Orderpage (e.g., FIG. 1E). A user device (e.g., using mobile device 102A orcomputer 102B) may navigate to external front end system 103 and requesta search by entering information into a search box. External front endsystem 103 may request information from one or more systems in system100. For example, external front end system 103 may request informationfrom FO System 113 that satisfies the search request. External front endsystem 103 may also request and receive (from FO System 113) a PromisedDelivery Date or “PDD” for each product included in the search results.The PDD, in some embodiments, may represent an estimate of when apackage containing the product will arrive at the user's desiredlocation or a date by which the product is promised to be delivered atthe user's desired location if ordered within a particular period oftime, for example, by the end of the day (11:59 PM). (PDD is discussedfurther below with respect to FO System 113.)

External front end system 103 may prepare an SRP (e.g., FIG. 1B) basedon the information. The SRP may include information that satisfies thesearch request. For example, this may include pictures of products thatsatisfy the search request. The SRP may also include respective pricesfor each product, or information relating to enhanced delivery optionsfor each product, PDD, weight, size, offers, discounts, or the like.External front end system 103 may send the SRP to the requesting userdevice (e.g., via a network).

A user device may then select a product from the SRP, e.g., by clickingor tapping a user interface, or using another input device, to select aproduct represented on the SRP. The user device may formulate a requestfor information on the selected product and send it to external frontend system 103. In response, external front end system 103 may requestinformation related to the selected product. For example, theinformation may include additional information beyond that presented fora product on the respective SRP. This could include, for example, shelflife, country of origin, weight, size, number of items in package,handling instructions, or other information about the product. Theinformation could also include recommendations for similar products(based on, for example, big data and/or machine learning analysis ofcustomers who bought this product and at least one other product),answers to frequently asked questions, reviews from customers,manufacturer information, pictures, or the like.

External front end system 103 may prepare an SDP (Single Detail Page)(e.g., FIG. 1C) based on the received product information. The SDP mayalso include other interactive elements such as a “Buy Now” button, a“Add to Cart” button, a quantity field, a picture of the item, or thelike. The SDP may further include a list of sellers that offer theproduct. The list may be ordered based on the price each seller offerssuch that the seller that offers to sell the product at the lowest pricemay be listed at the top. The list may also be ordered based on theseller ranking such that the highest ranked seller may be listed at thetop. The seller ranking may be formulated based on multiple factors,including, for example, the seller's past track record of meeting apromised PDD. External front end system 103 may deliver the SDP to therequesting user device (e.g., via a network).

The requesting user device may receive the SDP which lists the productinformation. Upon receiving the SDP, the user device may then interactwith the SDP. For example, a user of the requesting user device mayclick or otherwise interact with a “Place in Cart” button on the SDP.This adds the product to a shopping cart associated with the user. Theuser device may transmit this request to add the product to the shoppingcart to external front end system 103.

External front end system 103 may generate a Cart page (e.g., FIG. 1D).The Cart page, in some embodiments, lists the products that the user hasadded to a virtual “shopping cart.” A user device may request the Cartpage by clicking on or otherwise interacting with an icon on the SRP,SDP, or other pages. The Cart page may, in some embodiments, list allproducts that the user has added to the shopping cart, as well asinformation about the products in the cart such as a quantity of eachproduct, a price for each product per item, a price for each productbased on an associated quantity, information regarding PDD, a deliverymethod, a shipping cost, user interface elements for modifying theproducts in the shopping cart (e.g., deletion or modification of aquantity), options for ordering other product or setting up periodicdelivery of products, options for setting up interest payments, userinterface elements for proceeding to purchase, or the like. A user at auser device may click on or otherwise interact with a user interfaceelement (e.g., a button that reads “Buy Now”) to initiate the purchaseof the product in the shopping cart. Upon doing so, the user device maytransmit this request to initiate the purchase to external front endsystem 103.

External front end system 103 may generate an Order page (e.g., FIG. 1E)in response to receiving the request to initiate a purchase. The Orderpage, in some embodiments, re-lists the items from the shopping cart andrequests input of payment and shipping information. For example, theOrder page may include a section requesting information about thepurchaser of the items in the shopping cart (e.g., name, address, e-mailaddress, phone number), information about the recipient (e.g., name,address, phone number, delivery information), shipping information(e.g., speed/method of delivery and/or pickup), payment information(e.g., credit card, bank transfer, check, stored credit), user interfaceelements to request a cash receipt (e.g., for tax purposes), or thelike. External front end system 103 may send the Order page to the userdevice.

The user device may enter information on the Order page and click orotherwise interact with a user interface element that sends theinformation to external front end system 103. From there, external frontend system 103 may send the information to different systems in system100 to enable the creation and processing of a new order with theproducts in the shopping cart.

In some embodiments, external front end system 103 may be furtherconfigured to enable sellers to transmit and receive informationrelating to orders.

Internal front end system 105, in some embodiments, may be implementedas a computer system that enables internal users (e.g., employees of anorganization that owns, operates, or leases system 100) to interact withone or more systems in system 100. For example, in embodiments wheresystem 100 enables the presentation of systems to enable users to placean order for an item, internal front end system 105 may be implementedas a web server that enables internal users to view diagnostic andstatistical information about orders, modify item information, or reviewstatistics relating to orders. For example, internal front end system105 may be implemented as a computer or computers running software suchas the Apache HTTP Server, Microsoft Internet Information Services(IIS), NGINX, or the like. In other embodiments, internal front endsystem 105 may run custom web server software designed to receive andprocess requests from systems or devices depicted in system 100 (as wellas other devices not depicted), acquire information from databases andother data stores based on those requests, and provide responses to thereceived requests based on acquired information.

In some embodiments, internal front end system 105 may include one ormore of a web caching system, a database, a search system, a paymentsystem, an analytics system, an order monitoring system, or the like. Inone aspect, internal front end system 105 may comprise one or more ofthese systems, while in another aspect, internal front end system 105may comprise interfaces (e.g., server-to-server, database-to-database,or other network connections) connected to one or more of these systems.

Transportation system 107, in some embodiments, may be implemented as acomputer system that enables communication between systems or devices insystem 100 and mobile devices 107A-107C. Transportation system 107, insome embodiments, may receive information from one or more mobiledevices 107A-107C (e.g., mobile phones, smart phones, PDAs, or thelike). For example, in some embodiments, mobile devices 107A-107C maycomprise devices operated by delivery workers. The delivery workers, whomay be permanent, temporary, or shift employees, may utilize mobiledevices 107A-107C to effect delivery of packages containing the productsordered by users. For example, to deliver a package, the delivery workermay receive a notification on a mobile device indicating which packageto deliver and where to deliver it. Upon arriving at the deliverylocation, the delivery worker may locate the package (e.g., in the backof a truck or in a crate of packages), scan or otherwise capture dataassociated with an identifier on the package (e.g., a barcode, an image,a text string, an RFID tag, or the like) using the mobile device, anddeliver the package (e.g., by leaving it at a front door, leaving itwith a security guard, handing it to the recipient, or the like). Insome embodiments, the delivery worker may capture photo(s) of thepackage and/or may obtain a signature using the mobile device. Themobile device may send information to transportation system 107including information about the delivery, including, for example, time,date, GPS location, photo(s), an identifier associated with the deliveryworker, an identifier associated with the mobile device, or the like.Transportation system 107 may store this information in a database (notpictured) for access by other systems in system 100. Transportationsystem 107 may, in some embodiments, use this information to prepare andsend tracking data to other systems indicating the location of aparticular package.

In some embodiments, certain users may use one kind of mobile device(e.g., permanent workers may use a specialized PDA with custom hardwaresuch as a barcode scanner, stylus, and other devices) while other usersmay use other kinds of mobile devices (e.g., temporary or shift workersmay utilize off-the-shelf mobile phones and/or smartphones).

In some embodiments, transportation system 107 may associate a user witheach device. For example, transportation system 107 may store anassociation between a user (represented by, e.g., a user identifier, anemployee identifier, or a phone number) and a mobile device (representedby, e.g., an International Mobile Equipment Identity (IMEI), anInternational Mobile Subscription Identifier (IMSI), a phone number, aUniversal Unique Identifier (UUID), or a Globally Unique Identifier(GUID)). Transportation system 107 may use this association inconjunction with data received on deliveries to analyze data stored inthe database in order to determine, among other things, a location ofthe worker, an efficiency of the worker, or a speed of the worker.

Seller portal 109, in some embodiments, may be implemented as a computersystem that enables sellers or other external entities to electronicallycommunicate with one or more systems in system 100. For example, aseller may utilize a computer system (not pictured) to upload or provideproduct information, order information, contact information, or thelike, for products that the seller wishes to sell through system 100using seller portal 109.

Shipment and order tracking system 111, in some embodiments, may beimplemented as a computer system that receives, stores, and forwardsinformation regarding the location of packages containing productsordered by customers (e.g., by a user using devices 102A-102B). In someembodiments, shipment and order tracking system 111 may request or storeinformation from web servers (not pictured) operated by shippingcompanies that deliver packages containing products ordered bycustomers.

In some embodiments, shipment and order tracking system 111 may requestand store information from systems depicted in system 100. For example,shipment and order tracking system 111 may request information fromtransportation system 107. As discussed above, transportation system 107may receive information from one or more mobile devices 107A-107C (e.g.,mobile phones, smart phones, PDAs, or the like) that are associated withone or more of a user (e.g., a delivery worker) or a vehicle (e.g., adelivery truck). In some embodiments, shipment and order tracking system111 may also request information from warehouse management system (WMS)119 to determine the location of individual products inside of afulfillment center (e.g., fulfillment center 200). Shipment and ordertracking system 111 may request data from one or more of transportationsystem 107 or WMS 119, process it, and present it to a device (e.g.,user devices 102A and 102B) upon request.

Fulfillment optimization (FO) system 113, in some embodiments, may beimplemented as a computer system that stores information for customerorders from other systems (e.g., external front end system 103 and/orshipment and order tracking system 111). FO system 113 may also storeinformation describing where particular items are held or stored. Forexample, certain items may be stored only in one fulfillment center,while certain other items may be stored in multiple fulfillment centers.In still other embodiments, certain fulfilment centers may be designedto store only a particular set of items (e.g., fresh produce or frozenproducts). FO system 113 stores this information as well as associatedinformation (e.g., quantity, size, date of receipt, expiration date,etc.).

FO system 113 may also calculate a corresponding PDD (promised deliverydate) for each product. The PDD, in some embodiments, may be based onone or more factors. For example, FO system 113 may calculate a PDD fora product based on a past demand for a product (e.g., how many timesthat product was ordered during a period of time), an expected demandfor a product (e.g., how many customers are forecast to order theproduct during an upcoming period of time), a network-wide past demandindicating how many products were ordered during a period of time, anetwork-wide expected demand indicating how many products are expectedto be ordered during an upcoming period of time, one or more counts ofthe product stored in each fulfillment center 200, which fulfillmentcenter stores each product, expected or current orders for that product,or the like.

In some embodiments, FO system 113 may determine a PDD for each producton a periodic basis (e.g., hourly) and store it in a database forretrieval or sending to other systems (e.g., external front end system103, SAT system 101, shipment and order tracking system 111). In otherembodiments, FO system 113 may receive electronic requests from one ormore systems (e.g., external front end system 103, SAT system 101,shipment and order tracking system 111) and calculate the PDD on demand.

Fulfilment messaging gateway (FMG) 115, in some embodiments, may beimplemented as a computer system that receives a request or response inone format or protocol from one or more systems in system 100, such asFO system 113, converts it to another format or protocol, and forward itin the converted format or protocol to other systems, such as WMS 119 or3^(rd) party fulfillment systems 121A, 121B, or 121C, and vice versa.

Supply chain management (SCM) system 117, in some embodiments, may beimplemented as a computer system that performs forecasting functions.For example, SCM system 117 may forecast a level of demand for aparticular product based on, for example, a past demand for products, anexpected demand for a product, a network-wide past demand, anetwork-wide expected demand, a count products stored in eachfulfillment center 200, expected or current orders for each product, orthe like. In response to this forecasted level and the amount of eachproduct across all fulfillment centers, SCM system 117 may generate oneor more purchase orders to purchase and stock a sufficient quantity tosatisfy the forecasted demand for a particular product.

Warehouse management system (WMS) 119, in some embodiments, may beimplemented as a computer system that monitors workflow. For example,WMS 119 may receive event data from individual devices (e.g., devices107A-107C or 119A-119C) indicating discrete events. For example, WMS 119may receive event data indicating the use of one of these devices toscan a package. As discussed below with respect to fulfillment center200 and FIG. 2, during the fulfillment process, a package identifier(e.g., a barcode or RFID tag data) may be scanned or read by machines atparticular stages (e.g., automated or handheld barcode scanners, RFIDreaders, high-speed cameras, devices such as tablet 119A, mobiledevice/PDA 1198, computer 119C, or the like). WMS 119 may store eachevent indicating a scan or a read of a package identifier in acorresponding database (not pictured) along with the package identifier,a time, date, location, user identifier, or other information, and mayprovide this information to other systems (e.g., shipment and ordertracking system 111).

WMS 119, in some embodiments, may store information associating one ormore devices (e.g., devices 107A-107C or 119A-119C) with one or moreusers associated with system 100. For example, in some situations, auser (such as a part- or full-time employee) may be associated with amobile device in that the user owns the mobile device (e.g., the mobiledevice is a smartphone). In other situations, a user may be associatedwith a mobile device in that the user is temporarily in custody of themobile device (e.g., the user checked the mobile device out at the startof the day, will use it during the day, and will return it at the end ofthe day).

WMS 119, in some embodiments, may maintain a work log for each userassociated with system 100. For example, WMS 119 may store informationassociated with each employee, including any assigned processes (e.g.,unloading trucks, picking items from a pick zone, rebin wall work,packing items), a user identifier, a location (e.g., a floor or zone ina fulfillment center 200), a number of units moved through the system bythe employee (e.g., number of items picked, number of items packed), anidentifier associated with a device (e.g., devices 119A-119C), or thelike. In some embodiments, WMS 119 may receive check-in and check-outinformation from a timekeeping system, such as a timekeeping systemoperated on a device 119A-119C.

3^(rd) party fulfillment (3PL) systems 121A-121C, in some embodiments,represent computer systems associated with third-party providers oflogistics and products. For example, while some products are stored infulfillment center 200 (as discussed below with respect to FIG. 2),other products may be stored off-site, may be produced on demand, or maybe otherwise unavailable for storage in fulfillment center 200. 3PLsystems 121A-121C may be configured to receive orders from FO system 113(e.g., through FMG 115) and may provide products and/or services (e.g.,delivery or installation) to customers directly. In some embodiments,one or more of 3PL systems 121A-121C may be part of system 100, while inother embodiments, one or more of 3PL systems 121A-121C may be outsideof system 100 (e.g., owned or operated by a third-party provider).

Fulfillment Center Auth system (FC Auth) 123, in some embodiments, maybe implemented as a computer system with a variety of functions. Forexample, in some embodiments, FC Auth 123 may act as a single-sign on(SSO) service for one or more other systems in system 100. For example,FC Auth 123 may enable a user to log in via internal front end system105, determine that the user has similar privileges to access resourcesat shipment and order tracking system 111, and enable the user to accessthose privileges without requiring a second log in process. FC Auth 123,in other embodiments, may enable users (e.g., employees) to associatethemselves with a particular task. For example, some employees may nothave an electronic device (such as devices 119A-119C) and may insteadmove from task to task, and zone to zone, within a fulfillment center200, during the course of a day. FC Auth 123 may be configured to enablethose employees to indicate what task they are performing and what zonethey are in at different times of day.

Labor management system (LMS) 125, in some embodiments, may beimplemented as a computer system that stores attendance and overtimeinformation for employees (including full-time and part-time employees).For example, LMS 125 may receive information from FC Auth 123, WMS 119,devices 119A-119C, transportation system 107, and/or devices 107A-107C.

The particular configuration depicted in FIG. 1A is an example only. Forexample, while FIG. 1A depicts FC Auth system 123 connected to FO system113, not all embodiments require this particular configuration. Indeed,in some embodiments, the systems in system 100 may be connected to oneanother through one or more public or private networks, including theInternet, an Intranet, a WAN (Wide-Area Network), a MAN(Metropolitan-Area Network), a wireless network compliant with the IEEE802.11a/b/g/n Standards, a leased line, or the like. In someembodiments, one or more of the systems in system 100 may be implementedas one or more virtual servers implemented at a data center, serverfarm, or the like.

FIG. 2 depicts a fulfillment center 200. Fulfillment center 200 is anexample of a physical location that stores items for shipping tocustomers when ordered. Fulfillment center (FC) 200 may be divided intomultiple zones, each of which are depicted in FIG. 2. These “zones,” insome embodiments, may be thought of as virtual divisions betweendifferent stages of a process of receiving items, storing the items,retrieving the items, and shipping the items. So while the “zones” aredepicted in FIG. 2, other divisions of zones are possible, and the zonesin FIG. 2 may be omitted, duplicated, or modified in some embodiments.

Inbound zone 203 represents an area of FC 200 where items are receivedfrom sellers who wish to sell products using system 100 from FIG. 1A.For example, a seller may deliver items 202A and 202B using truck 201.Item 202A may represent a single item large enough to occupy its ownshipping pallet, while item 202B may represent a set of items that arestacked together on the same pallet to save space.

A worker will receive the items in inbound zone 203 and may optionallycheck the items for damage and correctness using a computer system (notpictured). For example, the worker may use a computer system to comparethe quantity of items 202A and 202B to an ordered quantity of items. Ifthe quantity does not match, that worker may refuse one or more of items202A or 202B. If the quantity does match, the worker may move thoseitems (using, e.g., a dolly, a handtruck, a forklift, or manually) tobuffer zone 205. Buffer zone 205 may be a temporary storage area foritems that are not currently needed in the picking zone, for example,because there is a high enough quantity of that item in the picking zoneto satisfy forecasted demand. In some embodiments, forklifts 206 operateto move items around buffer zone 205 and between inbound zone 203 anddrop zone 207. If there is a need for items 202A or 202B in the pickingzone (e.g., because of forecasted demand), a forklift may move items202A or 202B to drop zone 207.

Drop zone 207 may be an area of FC 200 that stores items before they aremoved to picking zone 209. A worker assigned to the picking task (a“picker”) may approach items 202A and 202B in the picking zone, scan abarcode for the picking zone, and scan barcodes associated with items202A and 202B using a mobile device (e.g., device 119B). The picker maythen take the item to picking zone 209 (e.g., by placing it on a cart orcarrying it).

Picking zone 209 may be an area of FC 200 where items 208 are stored onstorage units 210. In some embodiments, storage units 210 may compriseone or more of physical shelving, bookshelves, boxes, totes,refrigerators, freezers, cold stores, or the like. In some embodiments,picking zone 209 may be organized into multiple floors. In someembodiments, workers or machines may move items into picking zone 209 inmultiple ways, including, for example, a forklift, an elevator, aconveyor belt, a cart, a handtruck, a dolly, an automated robot ordevice, or manually. For example, a picker may place items 202A and 202Bon a handtruck or cart in drop zone 207 and walk items 202A and 202B topicking zone 209.

A picker may receive an instruction to place (or “stow”) the items inparticular spots in picking zone 209, such as a particular space on astorage unit 210. For example, a picker may scan item 202A using amobile device (e.g., device 119B). The device may indicate where thepicker should stow item 202A, for example, using a system that indicatean aisle, shelf, and location. The device may then prompt the picker toscan a barcode at that location before stowing item 202A in thatlocation. The device may send (e.g., via a wireless network) data to acomputer system such as WMS 119 in FIG. 1A indicating that item 202A hasbeen stowed at the location by the user using device 1198.

Once a user places an order, a picker may receive an instruction ondevice 1198 to retrieve one or more items 208 from storage unit 210. Thepicker may retrieve item 208, scan a barcode on item 208, and place iton transport mechanism 214. While transport mechanism 214 is representedas a slide, in some embodiments, transport mechanism may be implementedas one or more of a conveyor belt, an elevator, a cart, a forklift, ahandtruck, a dolly, or the like. Item 208 may then arrive at packingzone 211.

Packing zone 211 may be an area of FC 200 where items are received frompicking zone 209 and packed into boxes or bags for eventual shipping tocustomers. In packing zone 211, a worker assigned to receiving items (a“rebin worker”) will receive item 208 from picking zone 209 anddetermine what order it corresponds to. For example, the rebin workermay use a device, such as computer 119C, to scan a barcode on item 208.Computer 119C may indicate visually which order item 208 is associatedwith. This may include, for example, a space or “cell” on a wall 216that corresponds to an order. Once the order is complete (e.g., becausethe cell contains all items for the order), the rebin worker mayindicate to a packing worker (or “packer”) that the order is complete.The packer may retrieve the items from the cell and place them in a boxor bag for shipping. The packer may then send the box or bag to a hubzone 213, e.g., via forklift, cart, dolly, handtruck, conveyor belt,manually, or otherwise.

Hub zone 213 may be an area of FC 200 that receives all boxes or bags(“packages”) from packing zone 211. Workers and/or machines in hub zone213 may retrieve package 218 and determine which portion of a deliveryarea each package is intended to go to, and route the package to anappropriate camp zone 215. For example, if the delivery area has twosmaller sub-areas, packages will go to one of two camp zones 215. Insome embodiments, a worker or machine may scan a package (e.g., usingone of devices 119A-119C) to determine its eventual destination. Routingthe package to camp zone 215 may comprise, for example, determining aportion of a geographical area that the package is destined for (e.g.,based on a postal code) and determining a camp zone 215 associated withthe portion of the geographical area.

Camp zone 215, in some embodiments, may comprise one or more buildings,one or more physical spaces, or one or more areas, where packages arereceived from hub zone 213 for sorting into routes and/or sub-routes. Insome embodiments, camp zone 215 is physically separate from FC 200 whilein other embodiments camp zone 215 may form a part of FC 200.

Workers and/or machines in camp zone 215 may determine which routeand/or sub-route a package 220 should be associated with, for example,based on a comparison of the destination to an existing route and/orsub-route, a calculation of workload for each route and/or sub-route,the time of day, a shipping method, the cost to ship the package 220, aPDD associated with the items in package 220, or the like. In someembodiments, a worker or machine may scan a package (e.g., using one ofdevices 119A-119C) to determine its eventual destination. Once package220 is assigned to a particular route and/or sub-route, a worker and/ormachine may move package 220 to be shipped. In exemplary FIG. 2, campzone 215 includes a truck 222, a car 226, and delivery workers 224A and224B. In some embodiments, truck 222 may be driven by delivery worker224A, where delivery worker 224A is a full-time employee that deliverspackages for FC 200 and truck 222 is owned, leased, or operated by thesame company that owns, leases, or operates FC 200. In some embodiments,car 226 may be driven by delivery worker 224B, where delivery worker224B is a “flex” or occasional worker that is delivering on an as-neededbasis (e.g., seasonally). Car 226 may be owned, leased, or operated bydelivery worker 224B.

Referring to FIG. 3, a schematic block diagram illustrating an exemplaryembodiment of a network comprising computerized systems for managing andmonitoring services and modules, consistent with disclosed embodimentsis shown. As illustrated in FIG. 3, a system 300 may include amonitoring platform 310, a scheduler system 320, an applicationprogramming interface (API) 332, a webpage 334, and user devices 342Aand 342B, each of which may communicate with each other via a network.In some embodiments, API 332 may include a plurality of APIs and webpage334 may include a plurality of webpages. In some embodiments, API 332may be a mobile application programming interface (MAPI) configured toprovide information to and/or receive requests from mobile devices(e.g., a smartphone). Monitoring platform 310 may include a processor312, a memory 314, a database 316, and a back-office software 318.Scheduler system 320 may include a page response system 322 and a ruleapplication system 324. In some embodiments, the systems and componentsof system 300 may communicate with the other components of system 300via a direct connection, for example, using a cable. In some otherembodiments, system 300 may be a part of system 100 of FIG. 1A and maycommunicate with the other components of system 100 via a network or viaa direct connection, for example, using a cable. The systems andcomponents of system 300 may each comprise a single computer or may eachbe configured as a distributed computer system including multiplecomputers that interoperate to perform one or more of the processes andfunctionalities associated with the disclosed examples.

System 300 may comprise processors (e.g., processor 312), memories(e.g., memory 314), and databases (e.g., database 316). The processorsmay be one or more known processing devices, such as a microprocessorfrom the Pentium™ family manufactured by Intel™ or the Turion™ familymanufactured by AMD™. The processors may constitute a single core ormultiple core processor that executes parallel processes simultaneously.For example, the processors may use logical processors to simultaneouslyexecute and control multiple processes. The processors may implementvirtual machine technologies or other known technologies to provide theability to execute, control, run, manipulate, store, etc. multiplesoftware processes, applications, programs, etc. In another example, theprocessors may include a multiple-core processor arrangement configuredto provide parallel processing functionalities to allow system 300 toexecute multiple processes simultaneously. One of ordinary skill in theart would understand that other types of processor arrangements could beimplemented that provide for the capabilities disclosed herein.

The memories may store one or more operating systems that perform knownoperating system functions when executed by the processors,respectively. By way of example, the operating system may includeMicrosoft Windows, Unix, Linux, Android, Mac OS, iOS, or other types ofoperating systems. Accordingly, examples of the disclosed invention mayoperate and function with computer systems running any type of operatingsystem. The memories may be a volatile or non-volatile, magnetic,semiconductor, tape, optical, removable, non-removable, or other type ofstorage device or tangible computer readable medium.

The databases may include, for example, Oracle™ databases, Sybase™databases, or other relational databases or non-relational databases,such as Hadoop™ sequence files, HBase™, or Cassandra™. The databases mayinclude computing components (e.g., database management system, databaseserver, etc.) configured to receive and process requests for data storedin memory devices of the database(s) and to provide data from thedatabase(s). The databases may include NoSQL databases such as HBase,MongoDB™ or Cassandra™. Alternatively, the databases may includerelational databases such as Oracle, MySQL and Microsoft SQL Server. Insome embodiments, the databases may take the form of servers, generalpurpose computers, mainframe computers, or any combination of thesecomponents.

The databases may store data that may be used by the processors forperforming methods and processes associated with disclosed examples. Thedatabases may be located in the systems or components of system 300 or,alternatively, they may be in external storage devices located outsideof the systems or components of system 300. Data stored in the databasesmay include any suitable data associated with services or modules (e.g.,rule checker results from rule application system 324, module data,webpage data, user data, request data, parsed data from page responsesystem 322, rules to be used by rule application system 324, etc.).

User devices 342A or 342B may be a tablet, mobile device, computer, orthe like. User devices 342A or 342B may include a display. The displaymay include, for example, liquid crystal displays (LCD), light emittingdiode screens (LED), organic light emitting diode screens (OLED), atouch screen, and other known display devices. The display may showvarious information to a user. For example, it may display a webpage(e.g., FIGS. 1B-1E) that includes an implemented module or an option totest a service or module. User devices 342A or 342B may include one ormore input/output (I/O) devices. The I/O devices may include one or moredevices that allow user devices 342A or 342B to send and receiveinformation from user devices 342A or 342B or another device. The I/Odevices may include various input/output devices, a camera, amicrophone, a keyboard, a mouse-type device, a gesture sensor, an actionsensor, a physical button, an oratory input, etc. The I/O devices mayalso include one or more communication modules (not shown) for sendingand receiving information from monitoring platform 310 by, for example,establishing wired or wireless connectivity between the user devices342A or 342B and monitoring platform 310.

In some embodiments, the users associated with user devices 342A or 342Bmay be external users (e.g., customers that interact with API 332 orwebpage 334) or internal users (e.g., employees of an organization thatdevelops, owns, operates, or leases systems 100 or 300). Internal frontend system 105 may be implemented as a computer system that enables theusers associated with user devices 342A or 342B to interact with system300. For example, in some embodiments, internal front end system 105 maybe implemented as a web server that enables internal users associatedwith user devices 342A or 342B to modify services or modules, add newservices or modules, submit requests to test (e.g., performverifications on) services or modules, submit requests to implementservices or modules (e.g., services or modules may be implemented byinserting the service or module into a webpage), to view diagnostic andstatistical information about tested or implemented services or modules,etc. In some embodiments, internal front end system 105 may run customweb server software designed to receive and process requests fromsystems or devices depicted in systems 100 or 300, acquire informationfrom databases (e.g., database 316) and other data stores based on thoserequests, and provide responses to the received requests based onacquired information.

In some embodiments, monitoring platform 310 may receive a request froma user (e.g., internal users) or user device 342A to perform a test on atarget service or module. Monitoring platform 310 may send the requestto scheduler system 320. In some embodiments, scheduler system 320 may,based on a scheduled time or triggered by an event, automatically testservices or modules. In some embodiments, scheduler system 320 mayconcurrently test a plurality of services or modules. Scheduler system320 may log data associated with tests, including estimated run times ofthe tests, test results, or actual run times of the tests.

Based on the received request, page response system 322 may call atarget API 332 or a target webpage uniform resource link (URL). Based onthe call by page response system 322, target API 332 may retrieve awebpage with an implemented module (e.g., webpage may be SRP of FIG. 1B)or target webpage 334 may retrieve a webpage (e.g., a webpage may be SRPof FIG. 1B without an implemented module). API 332 or webpage 334 maysend the retrieved webpage to page response system 322.

Page response system 322 may parse the retrieved webpage by loading theURL (e.g., which references JSON or HTML code) for the retrieved webpageassociated with API 332 or the retrieved webpage associated with webpage334 and extracting data from the retrieved webpage. In some embodiments,user device 342A (e.g., associated with internal users) may specify thedata to be extracted from the webpage. In some embodiments, pageresponse system 322 may automatically determine the data to be extractedfrom the webpage based on characteristics of the webpage (e.g., theextracted data may include a type of search query on the webpage,product or item categories on the webpage, type of products or items onthe webpage for a specific category, type of products or items on thewebpage as a result of a search query, etc.). In some embodiments, pageresponse system 322 may send the retrieved webpage to rule applicationsystem 324 and rule application system 324 may retrieve at least onerule from database 316 based on the characteristics of the webpage. Pageresponse system 322 may determine the data to be extracted from thewebpage based on the retrieved rule. Page response system 322 may sendthe retrieved webpage or the extracted data from the webpage to ruleapplication system 324.

Rule application system 324 may apply the retrieved rule to the dataextracted from the webpage. The retrieved rule may include apredetermined condition for determining whether the webpage is normal orabnormal. For example, a rule may test the number of products thatappear on a webpage after a search query is submitted. The predeterminedcondition of the rule may be a number of products that appear on thewebpage after the search query is submitted. If the results of theapplied rule indicate that the number of products that appear on thewebpage is different from the predetermined condition, then ruleapplication system 324 may determine that the webpage is abnormal. Ifthe results of the applied rule indicate that the number of productsthat appear on the webpage is the same as the predetermined condition,then rule application system 324 may determine that the webpage isnormal.

In another example, a rule may test the number of products that appearon a webpage after a product category is selected. The predeterminedcondition of the rule may be a number of products that appear on thewebpage after the product category is selected. If the results of theapplied rule indicate that the number of products that appear on thewebpage is different from the predetermined condition, then ruleapplication system 324 may determine that the webpage is abnormal. Ifthe results of the applied rule indicate that the number of productsthat appear on the webpage is the same as the predetermined condition,then rule application system 324 may determine that the webpage isnormal.

In another example, a rule may test the types of products that appear ona webpage after a search query is submitted. For example, a search querymay include “dairy products.” The predetermined condition of the rulemay be only dairy products (e.g., cheese, yogurt, etc.) that appear onthe webpage after the search query is submitted. If the results of theapplied rule indicate that the type of products that appear on thewebpage is different from the predetermined condition, then ruleapplication system 324 may determine that the webpage is abnormal. Ifthe results of the applied rule indicate that the type of products thatappear on the webpage is the same as the predetermined condition, thenrule application system 324 may determine that the webpage is normal.

In another example, a rule may test the type of products that appear ona webpage after a product category is selected. For example, a productcategory may be “shoes.” The predetermined condition of the rule may beonly shoe products (e.g., sneakers, slippers, etc.) that appear on thewebpage after the product category is selected. If the results of theapplied rule indicate that the type of products that appear on thewebpage is different from the predetermined condition, then ruleapplication system 324 may determine that the webpage is abnormal. Ifthe results of the applied rule indicate that the type of products thatappear on the webpage is the same as the predetermined condition, thenrule application system 324 may determine that the webpage is normal.

In another example, a rule may test whether the correct images ofproducts appear on a webpage after a search query is submitted or aproduct category is selected. For example, a search query or productcategory may be “shoes.” The predetermined condition of the rule may beimages associated with each shoe product that appears on the webpageafter the search query is submitted or the product category is selected.If the results of the applied rule indicate that images are not loadedfor products or an incorrect image is loaded with a product, then ruleapplication system 324 may determine that the webpage is abnormal. Ifthe results of the applied rule indicate that correct images, as definedby predetermined conditions, are loaded for each product, then ruleapplication system 324 may determine that the webpage is normal.

Rule application system 324 may send the results of the applied rule tomonitoring platform 310. Based on the characteristics of the webpage andthe results of applied rule, monitoring platform 310 may, automaticallyor by user instruction, instruct rule application system 324 to send analert (e.g., by an instant messaging platform) or analytics of theresults (e.g., product or item identifications associated with thewebpage, product or item categories associated with the webpage, queriesassociated with the webpage, description of any webpage abnormalities,run time of applied rule, etc.) of the applied rule to at least one userdevice (e.g., user devices 342A or 342B associated with internal users).If the results indicate that the webpage is abnormal, then monitoringplatform 310 may not implement API 332 or webpage 334 to allow API 332or webpage 334 to be further developed (e.g., modified by user devicesor internal users). If the results indicate that the webpage is normal,then monitoring platform 310 may implement API 332 or webpage 334.Back-office software 318 may send a response to user device 342B wherethe response may include an indication of whether API 332 or webpage 334has been implemented, analytical data associated with the applied rule,an indication of whether alerts or analytics were sent to user devices342A or 342B, etc.

Referring to FIG. 4, a process 400 for managing and monitoring servicesand modules, consistent with disclosed embodiments is shown.

At step 401, monitoring platform 310 may receive a request from a user(e.g., internal users) or user device to perform a test on a targetservice or module. Monitoring platform 310 may send the request toscheduler system 320. In some embodiments, scheduler system 320 may,based on a scheduled time or triggered by an event, automatically testservices or modules. In some embodiments, scheduler system 320 mayconcurrently test a plurality of services or modules. Scheduler system320 may log data associated with tests, including estimated run times ofthe tests, test results, or actual run times of the tests.

Based on the received request, page response system 322 may call atarget API 332 or a target webpage URL. Based on the call by pageresponse system 322, target API 332 may retrieve a webpage with animplemented module (e.g., webpage may be SRP of FIG. 1B) or targetwebpage 334 may retrieve a webpage (e.g., a webpage may be SRP of FIG.1B without an implemented module). API 332 or webpage 334 may send theretrieved webpage to page response system 322.

Page response system 322 may parse the retrieved webpage by loading theURL (e.g., which references JSON or HTML code) for the retrieved webpageassociated with API 332 or the retrieved webpage associated with webpage334 and extracting data from the retrieved webpage. In some embodiments,user device 342A may specify the data to be extracted from the webpage.In some embodiments, page response system 322 may automaticallydetermine the data to be extracted from the webpage based oncharacteristics of the webpage (e.g., the extracted data may include atype of search query on the webpage, product or item categories on thewebpage, type of products or items on the webpage for a specificcategory, type of products or items on the webpage as a result of asearch query, etc.).

At step 403, page response system 322 may send the retrieved webpage torule application system 324 and rule application system 324 may retrieveat least one rule from database 316 based on the characteristics of thewebpage. Page response system 322 may determine the data to be extractedfrom the webpage based on the retrieved rule. Page response system 322may send the retrieved webpage or the extracted data from the webpage torule application system 324. Rule application system 324 may apply theretrieved rule to the data extracted from the webpage. The retrievedrule may include a predetermined condition for determining whether thewebpage is normal or abnormal. For example, a rule may test the numberof products that appear on a webpage after a search query is submitted.The predetermined condition of the rule may be a number of products thatappear on the webpage after the search query is submitted. If theresults of the applied rule indicate that the number of products thatappear on the webpage is different from the predetermined condition,then rule application system 324 may determine that the webpage isabnormal. If the results of the applied rule indicate that the number ofproducts that appear on the webpage is the same as the predeterminedcondition, then rule application system 324 may determine that thewebpage is normal.

Rule application system 324 may send the results of the applied rule tomonitoring platform 310. Based on the characteristics of the webpage andthe results of applied rule, monitoring platform 310 may, automaticallyor by user instruction, instruct rule application system 324 to send analert (e.g., by an instant messaging platform) or analytics of theresults (e.g., product or item identifications associated with thewebpage, product or item categories associated with the webpage, queriesassociated with the webpage, description of any webpage abnormalities,run time of applied rule, etc.) of the applied rule to user devices 342Aor 342B.

At step 405, if the results indicate that the webpage is abnormal, thenmonitoring platform 310 may not implement API 332 or webpage 334 toallow API 332 or webpage 334 to be further developed (e.g., modified byinternal users). If the results indicate that the webpage is normal,then monitoring platform 310 may implement API 332 or webpage 334.Back-office software 318 may send a response to a device or a user wherethe response may include an indication of whether API 332 or webpage 334has been implemented, analytical data associated with the applied rule,an indication of whether alerts or analytics were sent to user devices342A or 342B, etc.

While the present disclosure has been shown and described with referenceto particular embodiments thereof, it will be understood that thepresent disclosure can be practiced, without modification, in otherenvironments. The foregoing description has been presented for purposesof illustration. It is not exhaustive and is not limited to the preciseforms or embodiments disclosed. Modifications and adaptations will beapparent to those skilled in the art from consideration of thespecification and practice of the disclosed embodiments. Additionally,although aspects of the disclosed embodiments are described as beingstored in memory, one skilled in the art will appreciate that theseaspects can also be stored on other types of computer readable media,such as secondary storage devices, for example, hard disks or CD ROM, orother forms of RAM or ROM, USB media, DVD, Blu-ray, or other opticaldrive media.

Computer programs based on the written description and disclosed methodsare within the skill of an experienced developer. Various programs orprogram modules can be created using any of the techniques known to oneskilled in the art or can be designed in connection with existingsoftware. For example, program sections or program modules can bedesigned in or by means of .Net Framework, .Net Compact Framework (andrelated languages, such as Visual Basic, C, etc.), Java, C++,Objective-C, HTML, HTML/AJAX combinations, XML, or HTML with includedJava applets.

Moreover, while illustrative embodiments have been described herein, thescope of any and all embodiments having equivalent elements,modifications, omissions, combinations (e.g., of aspects across variousembodiments), adaptations and/or alterations as would be appreciated bythose skilled in the art based on the present disclosure. Thelimitations in the claims are to be interpreted broadly based on thelanguage employed in the claims and not limited to examples described inthe present specification or during the prosecution of the application.The examples are to be construed as non-exclusive. Furthermore, thesteps of the disclosed methods may be modified in any manner, includingby reordering steps and/or inserting or deleting steps. It is intended,therefore, that the specification and examples be considered asillustrative only, with a true scope and spirit being indicated by thefollowing claims and their full scope of equivalents.

What is claimed is:
 1. A computer-implemented system for managing andmonitoring services and modules, comprising: a memory storinginstructions; and at least one processor configured to execute theinstructions to: receive, from a user device, a request to perform atest on a target application programming interface; call the targetapplication programming interface; retrieve a search result pageassociated with the target application programming interface; retrieve arule based on the target application programming interface, wherein therule comprises: determining a number of products on the search resultpage when a product category is selected: determining types of productson the search result page when a search query is submitted; determiningtypes of products on the search result page when a product category isselected; or determining images of products on the search result pagewhen a search query is submitted or a product category is selected;apply the rule to the retrieved search result page associated with thetarget application programming interface; and based on the results ofthe applied rule, determine whether to implement the target applicationprogramming interface.
 2. The system of claim 1, wherein retrieving thesearch result page further comprises parsing the search result page. 3.The system of claim 2, wherein parsing the search result page comprises:loading a uniform resource link associated with the target applicationprogramming interface; and extracting data specified by the user devicefrom the search result page, wherein the rule is applied to theextracted data.
 4. The system of claim 3, wherein the extracted data isspecified based on the rule.
 5. The system of claim 1, wherein theresults indicate whether the search result page is normal or abnormal.6. The system of claim 5, wherein if the results indicate that thesearch result page is abnormal, then the instructions further comprise:sending an alert to the user device; and not implementing the targetapplication programming interface.
 7. The system of claim 6, wherein thealert comprises an item identification and a description of the searchresult page abnormality.
 8. The system of claim 5, wherein if theresults indicate that the search result page is normal, then theinstructions further comprise implementing the target applicationprogramming interface.
 9. The system of claim 1, wherein the rulefurther comprises a predetermined condition for determining whether thesearch result page is normal, the predetermined condition comprising: anumber of items on the search result page based on a search query; anumber of items on the search result page based on an item category;types of items on the search result page based on a query; or types ofitems on the search result page based on a category.
 10. The system ofclaim 1, wherein implementing the target application programminginterface comprises inserting the target application programminginterface into the search result page.
 11. A computer-implemented methodfor managing and monitoring services and modules, comprising: receiving,from a user device, a request to perform a test on a target applicationprogramming interface; calling the target application programminginterface; retrieving a search result page associated with the targetapplication programming interface; retrieving a rule based on the targetapplication programming interface, wherein the rule comprises:determining a number of products on the search result page when aproduct category is selected; determining types of products on thesearch result page when a search query is submitted; determining typesof products on the search result page when a product category isselected; or determining images of products on the search result pagewhen a search query is submitted or a product category is selected;applying the rule to the retrieved search result page associated withthe target application programming interface; and based on the resultsof the applied rule, determining whether to implement the targetapplication programming interface.
 12. The method of claim 11, whereinretrieving the search result page further comprises parsing the searchresult page.
 13. The method of claim 12, wherein parsing the searchresult page comprises: loading a uniform resource link associated withthe target application programming interface; and extracting dataspecified by the user device from the search result page, wherein therule is applied to the extracted data.
 14. The method of claim 13,wherein the extracted data is specified based on the rule.
 15. Themethod of claim 11, wherein the results indicate whether the searchresult page is normal or abnormal.
 16. The method of claim 15, whereinif the results indicate that the search result page is abnormal, themethod further comprises: sending an alert to the user device; and notimplementing the target application programming interface.
 17. Themethod of claim 16, wherein the alert comprises an item identificationand a description of the search result page abnormality.
 18. The methodof claim 15, wherein if the results indicate that the search result pageis normal, then the method further comprises implementing the targetapplication programming interface.
 19. The method of claim 11, whereinthe rule further comprises a predetermined condition for determiningwhether the search result page is normal, the predetermined conditioncomprising: a number of items on the search result page based on asearch query; a number of items on the search result page based on anitem category; types of items on the search result page based on aquery; or types of items on the search result page based on a category.20. A computer-implemented system for managing and monitoring servicesand modules, comprising: a memory storing instructions; and at least oneprocessor configured to execute the instructions to: receive, from auser device, a request to perform a test on a target applicationprogramming interface; call the target application programminginterface; retrieve a search result page associated with the targetapplication programming interface; retrieve a rule based on the targetapplication programming interface, wherein the rule comprises:determining a number of products on the search result page when aproduct category is selected; determining types of products on thesearch result page when a search query is submitted; determining typesof products on the search result page when a product category isselected; or determining images of products on the search result pagewhen a search query is submitted or a product category is selected; loada uniform resource link associated with the target applicationprogramming interface; extract data from the retrieved search resultpage, wherein the rule is applied to the extracted data and the userdevice specifies the extracted data in accordance with the rule; applythe rule to the extracted data from the retrieved search result pageassociated with the target application programming interface; and basedon the results of the applied rule, determine whether to implement thetarget application programming interface.